The supplied Sovereign Tower murder walkthrough reports one tested Gwendan route: observe the death, investigate with Gwendan, press his inconsistent account, rewind to before the event, temporarily dismiss him, and verify that the death no longer occurs.
Quick Answer
This sequence is evidence from a player's timeline, not a universal event script. The author separates Gwendan's personal debt from the murder and says paying it did not prevent the death. Information from the failed timeline, followed by a pre-event roster change, was the reported solution.
The useful pattern is investigation before intervention. Let the event reveal its evidence, assign Gwendan, confront him about contradictions until he describes strange influence, then return to a point marked before the murder and remove him from the Round Table. Continue beyond the former event window to confirm the result.
The victim varied between timelines according to the source. The timeline-dependent victim, exact event cycle, exact rewind point, debt cost, mechanical penalties, and achievement trigger are all To be confirmed.
Letting the Event Occur
In the reported information-gathering timeline, a Knight is found dead inside the Tower's private area. The event suggests that someone with internal access was involved, but the motive and method are not initially clear. Rather than immediately erasing the timeline, the author continues long enough to learn who can be investigated and what intervention may matter.
This does not mean every playthrough must permanently accept the death. It describes a use of the rewind structure: first collect information in a bad timeline, then use retained knowledge to alter an earlier point. The source does not establish the exact earliest trigger, a universal victim, or every prerequisite for the murder audience.
One named victim appears in the tested account, but the author explicitly warns that another timeline can select someone else. That name is not treated as a fixed route fact here. The victim and any character-specific consequences are To be confirmed for the current save.
Assigning the Investigation
The route's counterintuitive step is assigning Gwendan himself to investigate. In the tested timeline, his report returns with suspicious behavior and inconsistent evidence. That result narrows the inquiry from general distrust of the Round Table to a specific contradiction connected to Gwendan.
This is a reported experiment, not proof that Gwendan must always be selected or that another investigator cannot expose the route. The assignment timing, available investigator list, and exact report language may depend on timeline state. They remain To be confirmed beyond the supplied playthrough.
The practical reason for this step is the information it unlocks. Dismissing Gwendan before discovering the contradiction might avoid one event, but the research does not show that it advances his explanation or establishes why removal works. The documented sequence uses the failed timeline to gain that knowledge first.
Confrontation and Rewind
After the inconsistent report, the walkthrough describes summoning Gwendan and pressing beyond his initial denials. The author challenges conflicting testimony, questionable magical evidence, possible destruction of evidence, and his access to the private quarters. Continued questioning eventually leads him to describe threatening whispers and an influence he regards as magical or occult.
That account reframes the event as manipulation rather than a simple personal motive. It is still one source's route evidence. Exact dialogue choices, required number of prompts, hidden checks, and the nature of the influence are To be confirmed. This page does not recreate a missing interrogation script.
Once that information is known, the report uses Demon Power to return to a marker before the murder. No universal cycle number is supplied. Choose a point early enough that Gwendan can still be removed before the old event window, and keep the failed timeline available if possible for comparison.
Temporary Dismissal
The tested intervention is to dismiss Gwendan from the Round Table while the timeline is still before the murder. The walkthrough says this action is available from Tower View. After removal, the player continues through the period when the murder previously occurred and checks that the audience does not recur and the intended victim remains alive.
The same report describes three observations from that playthrough: dismissal appeared temporary, the interface said a dismissed Knight could later be invited through the Map Room, and Gwendan later appeared willing to return. All three claims are source-reported and To be confirmed. The recall timing, any fund cost, affinity impact, and quest effects are also To be confirmed.
Temporary absence can still reduce the active roster and remove one of the player's available specialists. The exact stat and scheduling impact depends on the current party, so no universal mechanical penalty is claimed. Verify that important assignments remain covered before advancing several cycles.
Timeline Variation
The walkthrough's strongest caution is that the victim can change. Its successful result is narrow: in one tested timeline, removing Gwendan before the event prevented that murder from appearing, and the intended victim remained alive several cycles beyond the original window. It does not prove that every later danger is removed or that every murder state behaves identically.
Verification should therefore compare event state rather than a fixed name or cycle. Note who is endangered in the failed timeline, rewind to a point the game identifies as earlier, make the roster change, then continue beyond the same relative window. Check both the missing murder audience and the character's continued presence.
If the event still occurs, that does not establish a different universal solution. It may mean the rewind was too late, the relevant dismissal did not happen, or the save has another route state. The precise dependency is To be confirmed.
Achievement Status
The source connects True Noble Soul with making Gwendan overcome his personal issues. It explicitly distinguishes that broader personal objective from merely identifying him in the investigation or preventing the murder. The author did not capture the achievement appearing on a specific final line.
Accordingly, the exact achievement trigger is To be confirmed. Continue Gwendan's later personal conversations after stabilizing the murder timeline, but do not assume that debt payment, dismissal, re-recruitment, the occult explanation, or saving one victim independently unlocks it.
The debt itself is another single-source precision issue. One report supplies a specific Gold amount and says payment did not prevent the murder; the related romance source also treats debt resolution as a separate personal branch. The exact cost, repayment behavior, affinity changes, and route effects remain To be confirmed.